flow_filtering/flow_filtering_mismatch_rule: Some mismatch rule packets match the rule

https://bugs.dpdk.org/show_bug.cgi?id=1606

Bug ID: 1606
Summary: flow_filtering/flow_filtering_mismatch_rule: Some
mismatch rule packets match the rule
Product: DPDK
Version: 24.11
Hardware: x86
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---

Environment
===========
DPDK version: a4f455560f version: 24.11-rc4
OS: Ubuntu24.04.1 LTS (Noble Numbat)/6.8.0-41-generic
Compiler: gcc version 13.2.0
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b NIC firmware:
FW: 9.50 0x8000f4e1 1.3682.0
Driver: i40e-2.26.8

Test Setup
Steps to reproduce
==================
1. bind ports to dpdk
./usertools/dpdk-devbind.py -b vfio-pci 0000:af:00.0 0000:af:00.1

2. build flow_filtering
meson configure -Dexamples=flow_filtering x86_64-native-linuxapp-gcc ninja -C x86_64-native-linuxapp-gcc

3. launch flow_filtering x86_64-native-linuxapp-gcc/examples/dpdk-flow_filtering -l 1 -n 4 -a 0000:af:00.0 -a 0000:af:00.1 -- --non-template

4. Send packets which mismatches the defined rule from tester sendp([Ether(dst='3c:fd:fe:cf:33:74')/IP(src='0.0.0.0', dst='192.169.1.1')/Raw(load=b'xxxxxxxxxxxxxxxxxxxx'),Ether(dst='3c:fd:fe:cf:33:74')/IP(src='0.0.0.0', dst='193.168.1.1')/Raw(load=b'xxxxxxxxxxxxxxxxxxxx')],iface="ens2f0",count=1,loop=0,inter=0.01)

5. Check the packets are not received by queue 1

Results:
========
EAL: Detected CPU lcores: 72
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
I40E_DRIVER: i40e_GLQF_reg_init(): i40e device 0000:af:00.0 changed global register [0x002689a0]. original: 0x00000021, new: 0x00000029
:: warn: 2 ports detected, but we use only one: port 0
:: initializing port: 0
:: initializing port: 0 done
Flow created!!:
src=00:00:00:00:00:00 - dst=3C:FD:FE:CF:33:74 - queue=0x1 src=00:00:00:00:00:00 - dst=3C:FD:FE:CF:33:74 - queue=0x1

Expected Result:
================
src=00:00:00:00:00:00 - dst=3C:FD:FE:CF:33:74 - queue=0x0 src=00:00:00:00:00:00 - dst=3C:FD:FE:CF:33:74 - queue=0x0

bad commit:
commit 16158f34900075f2f30b879bf3708e54e07455f4

Author: Shani Peretz <[email protected]>
Date:   Mon Sep 30 22:53:21 2024 +0300

examples/flow_filtering: introduce use cases snippets

These code snippets demonstrate rule creation using template and non-template APIs.
They include functions that enable developers to create rules. The purpose of providing these snippets is to allow developers to reuse them, thereby saving time and effort during the implementation of flow rules.

The code snippets are categorized based on their usage and can be copied, paste and modified to suit any requirements.
The snippets provided here are kept up to date and are being compiled along with the rest of the examples.

There is a skeleton that demonstrates rule creation using both template and non template APIs.

Developers can change the functions in the skeleton to the corresponding snippet functions with the appropriate suffix and create rules using the snippets themselves for easy testing. Each snippet has the same functions to implement the actions and patterns for the corresponding feature.

You are receiving this mail because:
You are the assignee for the bug.